home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19971216-19980424
/
000299_news@newsmaster….columbia.edu _Tue Mar 17 18:15:33 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id SAA01507
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 17 Mar 1998 18:15:32 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id SAA10420
for kermit.misc@watsun; Tue, 17 Mar 1998 18:15:31 -0500 (EST)
Path: news.columbia.edu!panix!news-peer.gip.net!news.gsl.net!gip.net!cpk-news-hub1.bbnplanet.com!cpk-news-feed4.bbnplanet.com!cpk-news-feed1.bbnplanet.com!news.bbnplanet.com!netnews.jhuapl.edu!usenet
From: Skip Collins <collibf1@jhuapl.edu>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: compiling ckermit with cygnus win32 tools
Date: 17 Mar 1998 17:53:57 -0500
Organization: Johns Hopkins University Applied Physics Lab, Laurel, MD, USA
Lines: 45
Sender: collibf1@COLLIBF1
Message-ID: <wk1zw1hqt6.fsf@jhuapl.edu>
References: <wken01miot.fsf@aplcomm.jhuapl.edu> <wk1zw1rrpp.fsf@jhuapl.edu>
<6emros$gdl@watsun.cc.columbia.edu>
NNTP-Posting-Host: collibf1-2.jhuapl.edu
X-Newsreader: Gnus v5.3/Emacs 19.34
Xref: news.columbia.edu comp.protocols.kermit.misc:8496
fdc@watsun.cc.columbia.edu (Frank da Cruz) writes:
> In article <wk1zw1rrpp.fsf@jhuapl.edu>,
> Skip Collins <collibf1@jhuapl.edu> wrote:
> :
> : After I compiled with -DNOUUCP and fixed the way I mounted COM1 and
> : COM2, serial transfer worked like a charm on a few simple tests.
> : Currently, the command line gets a little garbled. But that is
> : probably pretty easy to fix. Now, if I can go back and fix uucp lock
> : files, ncurses, and tcp, the end result should be pretty nice.
> :
> Nice for what purpose?
Nice for the same purposes that C-Kermit running on a Linux box is
nice: because it could provide a functional Kermit with some pretty
advanced features. I am not claiming that this should replace K95. I
am only doing it to get a feel for how well I can expect complex
programs to port. So far, I am pleasantly surprised.
> It would lack terminal emulation, XYZmodem file transfer, Windows
> Telephony, scrollback in command and terminal modes, mouse actions,
> printer control, Browser hotspots, keyboard mapping for all keys and
> key combinations, support for Windows code pages and/or Unicode, and
> countless other Windows-specific items that Windows users ask for.
But if I don't need those things, and if I don't need support, and if
it works well (a big if), why not?
> UNIX C-Kermit is designed for, and supported under, UNIX. If it can
> be compiled under Windows using UNIX compatibility libraries such as
> Cygwin-32, OpenWindows, or UWIN, it might or might not work; if it
> works, it might work well or poorly, but in any case the result is not
> supportable.
>
> We already have a mature and supported native product for Windows 95,
> one which is under constant development. There is no need to start
> over.
I am doing this mostly for fun. If I can get it working in two
afternoons, that would be worth it to me, if only for the experience
gained with the Cygnus tools. I do not intend to maintain a rival to
K95. Certainly, anyone needing a reliable Kermit on NT or 95 should
get K95. But for those who enjoy tinkering and learning a new
development environment, this is not a bad way to go.
Skip Collins